Repository navigation
docs(agent-gateway): add forwarding headers page - #1133
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The changes are documentation-only, with one minor example-completeness issue and no identified blocking defects.
1 open issue
What changed in this PR
Adds Agent Gateway documentation for forwarding client headers to upstream agents, with links from the navigation and Agent Registry.
Changes:
- Documents configuration modes, renaming, protected headers, and header precedence.
- Adds an A2A request example and explains forwarding scope.
- Makes the new page discoverable through existing Agent Gateway documentation.
| File | Description |
|---|---|
product/agent-gateway/registry.mdx |
Adds a card linking to header forwarding documentation. |
product/agent-gateway/forwarding-headers.mdx |
Documents forwarding configuration, restrictions, and usage. |
docs.json |
Adds the page to Agent Gateway navigation. |
Review effort: Balanced
Co-authored-by: narengogi <47327611+narengogi@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
The gateway implementation branch returned 404, preventing confirmation of the documented protected-header filtering, rename validation, case-insensitive credential precedence, and agent-card exclusions.
No open issues 🎉
1 resolved since last review
Review effort: Balanced
kiran-4444
approved these changes
Nov 11, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents
forward_headersfor agent integrations.Changes
product/agent-gateway/forwarding-headers.mdx, modeled on the MCP forwarding headers page: config forms, renames, headers that are never forwarded, header priority, an A2A exampleTesting